Audio summary based audio processing

ABSTRACT

In one aspect, audio summaries and transition audio segments are sequentially rendered with at least one transition audio segment rendered between each pair of sequential audio summaries. Each audio summary comprises digital content summarizing at least a portion of a respective associated audio piece. In another aspect, an original audio file is annotated by embedding therein information enabling rendering of at least one audio summary contained in the annotated audio file and comprising digital content summarizing at least a portion of the original audio file. In another aspect, an original audio file is annotated by providing at least one browsable link between the original audio file and at least one audio summary comprising digital content summarizing at least a portion of the original audio file, and storing the original audio file, the at least one browsable link, and the at least one audio summary on a common portable storage medium. In another aspect, an audio piece is divided into audio segments. Acoustical features are extracted from each audio segment. Audio segments are grouped into clusters based on the extracted features. A representative audio segment is identified in each cluster. A representative audio segment is selected as an audio summary of the audio piece.

TECHNICAL FIELD

This invention relates to audio summary based audio processing systems and methods.

BACKGROUND

Individuals and organizations are rapidly accumulating large collections of audio content. As these collections grow, individuals and organizations increasingly will require systems and methods for organizing and summarizing the audio content in their collections so that desired audio content may be found quickly and easily. To meet this need, a variety of different systems and methods for summarizing and browsing audio content have been proposed. For example, a variety of different audio summarization approaches have focused on generating and browsing audio thumbnails, which are short, representative portions of original audio pieces.

In one approach for generating audio thumbnails, an audio piece is divided into uniformly spaced segments. Mel frequency cepstral coefficients (MFCCs) are computed for each segment. The segments then are clustered by thresholding a symmetric KL (Kullback-Leibler) divergence measure. The longest component of the most frequent cluster is returned as an audio thumbnail.

Another audio thumbnail based approach analyzes the structure of digital music based on a similarity matrix, which contains the results of all possible pairwise similarity comparisons between time windows in a digital audio piece. The similarity matrix is used to visualize and characterize the structure of the digital audio piece. The digital audio piece is segmented by correlating a kernel along a diagonal of the similarity matrix. Once segmented, spectral characteristics of each segment are computed. Segments then are clustered based on the self-similarity of their statistics. The digital audio piece is summarized by selecting clusters with repeated segments through the file.

In one audio thumbnail based approach, computer readable data representing a musical piece is received and an audio summary that includes the main melody of the musical piece is generated. A component builder generates a plurality of composite and primitive components representing the structural elements of the musical piece and creates a hierarchical representation of the components. The most primitive components, representing notes within the musical piece, are examined to determine repetitive patterns within the composite components. A melody detector examines the hierarchical representation of the components and uses algorithms to detect which of the repetitive patterns is the main melody of the musical piece. Once the main melody is detected, the segment of the musical data containing the main melody is provided in one or more formats. Musical knowledge rules representing specific genres of musical styles may be used to assist the component builder and melody detector in determining which primitive component patterns are the most likely candidates for the main melody.

In one known method for skimming digital audio/video (A/V) data, the video data is partitioned into video segments and the audio data is transcribed. Representative frames from each of the video segments are selected. The representative frames are combined to form an assembled video sequence. Keywords contained in the corresponding transcribed audio data are identified and extracted. The extracted keywords are assembled into an audio track. The assembled video sequence and audio track are output together.

SUMMARY

In one aspect, the invention features an audio processing scheme in accordance with which audio summaries and transition audio segments are sequentially rendered with at least one transition audio segment rendered between each pair of sequential audio summaries. Each audio summary comprises digital content summarizing at least a portion of a respective associated audio piece.

In another aspect, the invention features a scheme for generating an annotated audio file. In accordance with this inventive scheme, an original audio file is annotated by embedding therein information enabling rendering of at least one audio summary contained in the annotated audio file and comprising digital content summarizing at least a portion of the original audio file.

In another aspect of the invention, an original audio file is annotated by providing at least one browsable link between the original audio file and at least one audio summary comprising digital content summarizing at least a portion of the original audio file, and storing the original audio file, the at least one browsable link, and the at least one audio summary on a common portable storage medium.

In another aspect, the invention features a portable medium that is readable by an electronic device and tangibly stores an original audio file, at least one audio summary comprising digital content summarizing at least a portion of an original audio file, and at least one browsable link between the original audio file and the at least one audio summary.

In another aspect of the invention, an audio piece is divided into audio segments. Acoustical features are extracted from each audio segment. Audio segments are grouped into clusters based on the extracted features. A representative audio segment is identified in each cluster. A representative audio segment is selected as an audio summary of the audio piece.

Other features and advantages of the invention will become apparent from the following description, including the drawings and the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an embodiment of a system for generating and rendering audio summaries and annotated audio files.

FIG. 2 is a flow diagram of an embodiment of a method of generating an audio summary.

FIG. 3 is a flow diagram of an embodiment of a method of generating an annotated audio file.

FIG. 4A is a diagrammatic view of audio summary rendering information embedded in a header of an audio file.

FIG. 4B is a diagrammatic view of audio summary rendering information embedded at different locations in an audio file.

FIG. 5 is a diagrammatic view of multiple audio summaries each linked to a respective audio file configured for storage on a portable storage medium.

FIG. 6 is a flow diagram of an embodiment of a method of rendering an annotated audio file.

FIG. 7 is a diagrammatic view of a sequence of audio summaries and transition audio segments and audio pieces respectively linked to associated audio summaries in the sequence.

FIG. 8 is a diagrammatic view of a pair of audio pieces being browsed by means of associated audio summaries.

DETAILED DESCRIPTION

In the following description, like reference numbers are used to identify like elements. Furthermore, the drawings are intended to illustrate major features of exemplary embodiments in a diagrammatic manner. The drawings are not intended to depict every feature of actual embodiments nor relative dimensions of the depicted elements, and are not drawn to scale.

As used herein, “audio summary” refers to any digital content that summarizes (i.e., represents, symbolizes, or brings to mind) the content of an associated original audio piece. An audio piece may be any form of audio content, including music, speech, audio portions of a movie or video, or other sounds. The digital content of an audio summary may be in the form of one or more of text, audio, graphics, animated graphics, and full-motion video. For example, in some implementations, an audio summary may be an audio thumbnail (i.e., a representative sample or portion of an audio piece).

The audio summaries that are browsed and rendered in the embodiments described below may be generated by any known or yet to be developed method, process, or means. For example, in some implementations, audio summaries are generated by randomly selecting segments (or thumbnails) of respective audio pieces. Each segment may have the same or different rendering duration (or length). In another example, audio thumbnails may be automatically generated by extracting segments of respective audio pieces in accordance with predefined rules (e.g., segments of predefined lengths and starting locations may be extracted from near the beginnings or endings of respective audio pieces). In some instances, at least some audio summaries are generated by the method described in section II below.

I. System Overview

Referring to FIG. 1, in one embodiment, a system for generating and rendering audio summaries and annotated audio files includes an audio summary generating engine 8, an audio file annotating engine 10, and rendering engine 12. These engines 8-12 may be configured to operate on any suitable electronic device, including a computer (e.g., desktop, laptop and handheld computer), a digital audio player, or any suitable audio capturing, audio editing, or audio rendering system.

In a computer-based implementation, audio summary generating engine 8, audio file annotating engine 10, and rendering engine 12 may be implemented as one or more respective software modules operating on a computer 30. Computer 30 includes a processing unit 32, a system memory 34, and a system bus 36 that couples processing unit 32 to the various components of computer 30. Processing unit 32 may include one or more processors, each of which may be in the form of any one of various commercially available processors. System memory 34 may include a read only memory (ROM) that stores a basic input/output system (BIOS) containing start-up routines for computer 30 and a random access memory (RAM). System bus 36 may be a memory bus, a peripheral bus or a local bus, and may be compatible with any of a variety of bus protocols, including PCI, VESA, Microchannel, ISA, and EISA. Computer 30 also includes a persistent storage memory 38 (e.g., a hard drive, a floppy drive 126, a CD ROM drive, magnetic tape drives, flash memory devices, and digital video disks) that is connected to system bus 36 and contains one or more computer-readable media disks that provide non-volatile or persistent storage for data, data structures and computer-executable instructions. A user may interact (e.g., enter commands or data) with computer 30 using one or more input devices 40 (e.g., a keyboard, a computer mouse, a microphone, joystick, and touch pad). Information may be presented through a graphical user interface (GUI) that is displayed to the user on a display monitor 42, which is controlled by a display controller 44. Audio may be rendered by an audio rendering system 45, which may include a sound card and one or more speakers. One or more remote computers may be connected to computer 30 through a network interface card (NIC) 46.

As shown in FIG. 1, system memory 34 also stores audio summary generating engine 8, audio file annotating engine 10, rendering engine 12, a GUI driver 48, and a database 50 containing one or more audio summaries, original audio files, and annotated audio files. In some implementations, audio summary generating engine 8 and audio file annotating engine 10 both interface with the GUI driver 48, the original audio files, and the user input 40 to control the generation of audio summaries and annotated audio files, respectively. Rendering engine 12 interfaces with audio rendering system 45, the audio summaries, the original audio files, and the annotated audio files to enable a user to playback and browse the collection of audio content in database 50. The audio summaries, the original audio files, and the annotated audio files in the collection to be rendered and browsed may be stored locally in persistent storage memory 38 or stored remotely and accessed through NIC 46, or both.

II. Generating Audio Summaries

Referring to FIG. 2, in some embodiments, audio summary generating engine 8 generates an audio summary of an audio piece as follows. The audio piece is divided into audio segments (step 60). In some implementations, the audio piece is divided into segments having substantially the same length (e.g., segments have a rendering duration of a preselected number of seconds). Acoustical features are extracted from each audio segment (step 62). The acoustical features may correspond to one or more types of acoustical features, including tonality, beat frequencies, and loudness. The audio segments are grouped into clusters based on the extracted acoustical features (step 64). The audio segments may be grouped into a preselected number of clusters. In some implementations, the audio segments are grouped into clusters using an LBG vector quantizer design algorithm (see, e.g., Linde, Y., Buzo, A., and Gray, R. M., “An algorithm for vector quantizer design,” IEEE Transactions on Communications COM-28, pp.84-95 (1980), which is incorporated herein by reference). A representative audio segment is identified in each cluster (step 66). In some implementations, a centroid of a preselected acoustical feature vector is computed for each cluster and the audio segment in each cluster that is closest to the centroid is identified as the representative audio segment for the corresponding cluster. From the set of representative audio segments, one representative audio segment is selected as an audio summary of the audio piece (step 68). In some implementations, clusters are ranked in order of the respective numbers of audio segments in the clusters and the representative segment of the highest ranking cluster is selected as the audio summary for the audio piece.

III. Generating Annotated Audio Files

The embodiments described below feature systems and methods of generating annotated audio files from original audio files, which may or may not have been previously annotated. An audio file is a stored representation of an audio piece. An audio file may be formatted in accordance with any uncompressed or compressed digital audio format (e.g., CD-Audio, DVD-Audio, WAV, AIFF, WMA, and MP3). An audio file may be annotated by associating with the audio file information enabling the rendering of at least one audio summary that includes digital content summarizing at least a portion of the associated original audio file. In some embodiments, an annotated audio file is generated by embedding information enabling the rendering of at least one audio summary that is contained in the annotated audio file. In other embodiments, an audio file is annotated by linking at least one audio summary to the original audio file and storing the linked audio summary and the original audio file together on the same portable storage medium. In this way, the audio summaries are always accessible to a rendering system because the contents of both the original audio file and the audio summaries are stored together either as a single file or as multiple linked files on a common storage medium. Users may therefore quickly and efficiently browse through a collection of annotated audio files without risk that the audio summaries will become disassociated from the corresponding audio files, regardless of the way in which the audio files are transmitted from one rendering system to another.

A. Embedding Audio Summary Rendering Information

Referring to FIG. 3, in some embodiments, an annotated audio file may be generated as follows. Audio file annotating engine 10 obtains an original audio file (step 90). Audio file annotating engine 10 also obtains information that enables at least one audio summary to be rendered (step 92). Audio file annotating engine 10 annotates the original audio file by embedding the audio summary rendering information in the original audio file (step 94).

Referring to FIGS. 4A and 4B, in some embodiments, audio summary rendering information 96 is embedded in the header 98 of an original audio file 100 (FIG. 4A). In other embodiments, audio summary rendering information 102, 104, 106 are embedded at different respective locations (e.g., locations preceding each segment or paragraph) of an original audio file 108 separated by audio content of the original audio file 108 (FIG. 4B). In some of these embodiments, pointers 110, 112 to the locations of the other audio summary rendering information 104, 106 may be embedded in the header of the original audio file 108, as shown in FIG. 4B.

In some implementations, the audio summary rendering information that is embedded in the original audio file corresponds to the audio summary itself. As mentioned above, an audio summary is any digital content (e.g., text, audio, graphics, animated graphics, and full-motion video) that summarizes (i.e., represents, symbolizes, or brings to mind) the content of the associated original audio file. Accordingly, in these implementations, the digital contents of the audio summaries are embedded in the original audio files. An embedded audio summary may be generated in any of the ways described herein. In some implementations, an audio summary may be derived from the original audio file (e.g., an audio thumbnail). In other implementations, an audio summary may be obtained from sources other than the original audio file yet still be representative of the original audio file (e.g., a trailer of a commercial motion picture, an audio or video clip, or a textual description of the original audio file).

Referring back to FIG. 3, after the audio file has been annotated, audio file annotating engine 10 stores the annotated audio file (step 114). For example, the annotated audio file may be stored in persistent storage memory 38 (FIG. 1).

B. Linking and Storing Audio Summaries and Original Audio Files

In some embodiments, an annotated audio file may be generated by linking at least one audio summary to the original audio file and storing the linked audio summary and original audio file together on the same portable storage medium. In this way, the original audio file is annotated by the one or more linked audio summaries. The links between audio summaries and original audio files may be stored in the audio summaries or in the original audio files. For example, the links may be stored in the headers of the audio summaries or in the headers of the original audio files, or both. Each link contains at least one location identifier (e.g., a file locator or a Uniform Resource Locator (URL)) that enables rendering engine 12 to browse from an audio summary to the linked original audio file, or vice versa. The portable storage medium may be any portable storage device on which digital audio summaries and original digital audio files may be stored, including CD-ROMs, rewritable CDs, DVD-ROMs, rewritable DVDs, laser disks, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks of portable electronic devices and removable hard disks), and magneto-optical disks.

In these embodiments, rendering engine 12 is configured to detect whether one or more audio summaries are stored on a portable storage medium. If at least one audio summary is detected, rendering engine 12 renders the audio summary and the linked original audio file in accordance with predetermined rendering rules. For example, rendering engine 12 first may render all of the audio summaries in a predefined sequence. During the rendering of each audio summary, a user may request that rendering engine 12 render the original audio file linked to the audio summary currently being rendered. In this way, the user may quickly browse the collection of original audio files stored on the portable storage medium. If rendering engine 12 detects original audio files on portable storage medium but does not detect any audio summaries on the portable storage medium, rendering engine 12 may render the detected original audio files in accordance with any known audio file playback method (e.g., automatically render each original audio file in a predefined sequence).

FIG. 5 shows an exemplary embodiment in which each of multiple audio summaries 116, 118, 120 is linked to a respective original audio file 122, 124, 126 by respective links (or pointers) 128, 130, 132. The audio summaries 116, 118, 120, original audio files 122-126, and links 128-132 are stored on the same portable storage medium. Rendering engine 12 recognizes each link 128-132 and follows each link between pairs of linked audio summaries and original audio files. In one exemplary implementation, the original audio files 122-126 are numbered tracks of digital audio music and the audio summaries 116-120 are digital contents summarizing each of the linked original audio files. The links 128-132 may be implemented by associating with each audio summary the same track number of the associated original audio file. In this way, if enabled to detect audio summaries, rendering engine 12 identifies linked pairs of audio summaries and original audio files by track number. An un-enabled audio rendering engine (e.g., a conventional digital music CD player) ignores the undetected audio summaries and rendering the original audio files (or tracks) in a conventional way. In the implementation illustrated in FIG. 5, N is an integer greater than two and, therefore, FIG. 5 shows a representation of three or more sets of linked audio summaries and original audio files. In other implementations, fewer than three sets of linked audio summaries and original audio files are stored on the same portable storage medium.

IV. Rendering Annotated Audio Files

Referring to FIG. 6, in some embodiments, an annotated audio file may be rendered by rendering engine 12 as follows. Rendering engine 12 obtains an audio file that has been annotated in one or more of the ways described in section III above (step 134). Rendering engine 12 identifies audio summary rendering information that is embedded in or linked to the annotated audio file (step 136). As explained above, the audio summary rendering information may correspond to one or more audio summaries that are embedded in or linked to the header or other locations of the annotated audio file. Alternatively, the audio summary rendering information may correspond to one or more pointers to locations where respective audio summaries are embedded in or linked to the annotated audio file. Based on the audio summary rendering information, rendering engine 12 enables a user to browse the summaries embedded in or linked to the annotated audio file (step 138). Rendering engine 12 initially may render audio summaries at the lowest (i.e., most coarse) level of detail. For example, in some implementations, rendering engine 12 initially may present to the user the highest ranking audio summaries representative of clusters of audio segments identified by the audio summary generating method described above in section II. If the user requests summaries to be presented at a greater level of detail, rendering engine 12 may render the audio summaries at a greater level of detail (e.g., render all of the audio summaries in a particular cluster).

In some implementations, while the user is browsing audio summaries, the user may select a particular summary as corresponding to the starting point for rendering the original audio file. In response, rendering engine 12 renders the original audio file beginning at the point corresponding to the audio summary selected by the user (step 139).

V. Rendering An Audio Sequence Including Audio Summaries

Referring to FIG. 7, in some embodiments, rendering engine 12 may render audio summaries 140, 142, 144 in an audio sequence 145. The audio summaries 140-144 are separated by respective transition audio segments 146, 148, 150. The audio summaries 140-144 and transition audio segments 146-150 may be concatenated and rendered in real time. In the illustrated embodiment, rendering engine 12 sequentially renders audio summaries 140-144 and transition audio segments 146-150 with one transition audio segment rendered between each pair of sequential audio summaries. In some implementations, rendering engine 12 renders all of the audio summaries 140-144 normalized to the same loudness level. Audio pieces 152, 154, 156 are linked to a corresponding representative audio summary 140, 142, 144. In some implementations, one or more audio pieces may be linked to multiple representative audio summaries that are incorporated into audio sequence 145. In the implementation illustrated in FIG. 7, M is an integer greater than two and, therefore, FIG. 7 shows a representation of three or more sets of linked audio summaries and audio pieces. In other implementations, fewer than three sets of linked audio summaries and audio pieces are incorporated into audio sequence 145.

As used herein, the term “transition audio segment” refers to any form of audio content that is sufficiently different from the audio summaries that a user is able to distinguish the transition audio segments from the audio summaries. The transition audio segments in audio sequence 145 may be the same or they may be different. In some implementations, each of the transition audio segments corresponds to a monotone sound. In other implementations, each of the transition audio segments is represented in the time domain by a Gaussian weighted sinusoid (or Gabor function) with a characteristic center frequency and width (or standard deviation). The center frequency of the Gabor function may be in the middle of the audible frequency range. In one implementation, the center frequency of the Gabor function is in the range of about 150-250 Hz. In some implementations, the center frequency of the Gabor function representing a transition audio segment has a center frequency that substantially corresponds to the center pitch of an adjacent audio summary in the sequence (e.g., either the audio summary preceding or following the transition audio segment in audio sequence 145).

In some implementations, the audio summaries 140-144 and transition audio segments 146-150 are rendered consecutively, with no gaps between the audio summaries and the transition audio segments. In one exemplary implementation, each audio summary 140-144 is three seconds long and each transition audio segment is one second long. Assuming that each audio summary is associated with a different respective audio piece, a user may browse three hundred audio pieces in twenty minutes. If each original audio piece is three minutes long, for example, it would take fifteen hours for a user to listen to all three hundred audio pieces. That is, by rendering audio summaries rendering engine 12 enables a user to browse all three hundred audio pieces forty five times faster than if the original audio pieces were rendered.

In some implementations, each audio piece is associated with a hierarchical cluster of audio summaries. In these implementations, during rendering of a given audio summary, a user may request the rendering engine 12 to render additional audio summaries in the same cluster. In response, the rendering audio engine 12 may render audio summaries in the cluster in accordance with the predefined hierarchical order until the user requests to resume the rendering of the audio sequence 145.

In some implementations, a user may interact with a graphical user interface to specify a category for each audio summary while the sequence 145 of audio summaries and transition audio segments are being rendered. In some implementations, during the rendering of a given audio summary a user may specify an input (e.g., “yes” or “no”) indicating whether or not the audio piece associated with the given audio summary should be added to a playlist. The rendering engine 12 stores the user-specified categories and builds one or more playlists based on the stored categories.

Referring to FIG. 8, in some implementations, each audio summary may be associated with a pointer to a location in an audio piece (e.g., the location in the audio piece from which the audio summary was extracted). In these implementations, rendering engine 12 allows the user to jump back and forth between rendering audio summaries and rendering audio pieces. For example, rendering engine 12 initially may begin to render the sequence 145 of audio summaries 140-144 and transition audio segments 146-150. In response to user input at time T₁, rendering engine 12 follows a pointer from a given audio summary 140 being rendered to the corresponding audio piece 152 and begins rendering the audio piece 152 at the location specified by the pointer. In response to user input at time T₂, rendering engine 12 terminates rendering of audio piece 82 and resumes rendering audio sequence 145 by rendering transition audio segment 146 followed by audio summary 142. In response to user input at time T₃, rendering engine 12 follows a pointer from a given audio summary 142 being rendered to the corresponding audio piece 154 and begins rendering the audio piece 154 at the location specified by the pointer. If the end of the audio piece 154 is reached without any intervening user input, the rendering engine 12 resumes rendering audio sequence 145 by rendering the successive transition audio segment 148 after the end of audio piece 154 has been rendered (i.e., at time T₄).

In some implementations, rendering engine 12 is configured to render each audio piece beginning at the location of its associated audio summary. Rendering engine 12 renders the entire audio piece unless it receives user input. The user input may correspond to a preselected category, such as “yes” or “no”, indicating whether or not to add the particular piece being rendered to a playlist. In response to user input or after the current audio piece has been rendered, the rendering engine 12 begins to render the successive audio piece beginning at the location of its associated audio summary. In some implementations, if an audio piece ends without any user category selection, the audio piece is added to the current playlist (e.g., “yes” category) by default.

In some embodiments, rendering engine 12 is configured to allow a user to browse audio summaries based on a similarity measure. In these embodiments, audio summary generating engine 8 sorts audio summaries based on their acoustic feature vector distances to one another. One or more acoustical features may be used in the computation of acoustic feature vector distances. Feature vector distances may be computed using any one of a wide variety of acoustic feature vector distance measures. In response to a user request to browse based on similarity, rendering engine 12 begins rendering the audio summaries in order of feature vector closeness to the audio summary that was being rendered when the user request was received.

VI. CONCLUSION

Other embodiments are within the scope of the claims.

The systems and methods described herein are not limited to any particular hardware or software configuration, but rather they may be implemented in any computing or processing environment, including in digital electronic circuitry or in computer hardware, firmware, or software. 

1. An audio processing method, comprising: sequentially rendering audio summaries and transition audio segments with at least one transition audio segment rendered between each pair of sequential audio summaries, wherein each audio summary comprises digital 5 content summarizing at least a portion of a respective associated audio piece.
 2. The method of claim 1, wherein identical transition audio segments are rendered between pairs of sequential audio summaries.
 3. The method of claim 2, wherein each identical transition audio segment corresponds to a Gabor function in a time domain representation.
 4. The method of claim 3, wherein each Gabor function has a center frequency substantially corresponding to a center pitch of an adjacent audio summary.
 5. The method of claim 1, wherein the audio summaries and the interleaved transition audio segments are rendered consecutively.
 6. The method of claim 1, wherein each audio summary is a representative segment of a respective associated audio piece.
 7. The method of claim 1, further comprising classifying audio pieces into categories in response to user input received during rendering of the associated audio summaries.
 8. The method of claim 7, further comprising building a playlist based on categories assigned to a set of audio pieces.
 9. The method of claim 1, wherein at least one audio summary is linked to an associated audio piece.
 10. The method of claim 9, further comprising rendering an audio piece linked to an associated audio summary in response to user input received during rendering of the associated audio summary.
 11. The method of claim 1, further comprising rendering a given audio piece beginning at a location in the given audio piece linked to an audio summary associated with the given audio piece.
 12. The method of claim 11, further comprising rendering a second audio piece at a location in the second audio piece linked to a successive audio summary associated with the second audio piece.
 13. The method of claim 1, further comprising ordering audio summaries in a sequence based on similarity to a given audio summary.
 14. The method of claim 13, wherein audio summaries are rendered in accordance with the ordered sequence.
 15. The method of claim 1, wherein each audio piece is associated with multiple audio summaries and a single audio summary is rendered automatically for each audio piece, and further comprising rendering an audio summary for a given audio piece in response to user input received during rendering of a preceding audio summary associated with the given audio piece.
 16. The method of claim 1, further comprising normalizing audio summaries to a common loudness level.
 17. An audio processing system, comprising: a rendering engine operable to sequentially render audio summaries and transition audio segments with at least one transition audio segment rendered between each pair of sequential audio summaries.
 18. A method of generating an annotated audio file, comprising: annotating an original audio file by embedding therein information enabling rendering of at least one audio summary contained in the annotated audio file and comprising digital content summarizing at least a portion of the original audio file.
 19. The method of claim 18, wherein the rendering enabling information is embedded in a header of the audio file.
 20. The method of claim 19, wherein rendering enabling information includes an audio summary embedded in the audio file header.
 21. The method of claim 19, wherein rendering enabling information embedded in the audio file header includes one or more pointers to one or more respective locations in the original audio file.
 22. The method of claim 18, wherein rendering enabling information is embedded at different locations in the annotated audio file separated by audio content of the original audio file.
 23. The method of claim 22, wherein rendering enabling information includes audio summaries embedded at different respective locations in the annotated audio file separated by audio content of the original audio file.
 24. The method of claim 22, wherein rendering enabling information includes pointers to locations in the original audio file, the pointers being embedded at different respective locations in the annotated audio file separated by audio content of the original audio file.
 25. The method of claim 18, wherein rendering enabling information includes hierarchical information enabling rendering of audio summaries at different levels of detail.
 26. The method of claim 18, wherein at least one audio summary corresponds to a representative sample of the original audio file.
 27. The method of claim 18, wherein at least one audio summary corresponds to audio content not contained in the original audio file.
 28. The method of claim 18, wherein at least one audio summary corresponds to one or more images representative of original audio file content.
 29. The method of claim 18, wherein at least one audio summary corresponds to digital textual content.
 30. A software program for generating an annotated audio file, the software program residing on a medium readable by an electronic device and comprising instructions for causing an electronic device to: annotate an original audio file by embedding therein information enabling rendering of at least one audio summary contained in the annotated audio file and comprising digital content summarizing at least a portion of the original audio file.
 31. A method of generating an annotated audio file, comprising: annotating an original audio file by providing at least one browsable link between the original audio file and at least one audio summary comprising digital content summarizing at least a portion of the original audio file, and storing the original audio file, the at least one browsable link, and the at least one audio summary on a common portable storage medium.
 32. A portable medium readable by an electronic device and tangibly storing an original audio file, at least one audio summary comprising digital content summarizing at least a portion of an original audio file, and at least one browsable link between the original audio file and the at least one audio summary.
 33. A system for rendering an annotated video file, comprising: a rendering engine operable to identify information embedded in the annotated audio file and enabling rendering of at least one audio summary contained in the annotated audio file and comprising digital content summarizing at least a portion of the original audio file, and to operable to render the at least one audio summary.
 34. An audio processing method, comprising: dividing an audio piece into audio segments; extracting acoustical features from each audio segment; grouping audio segments into clusters based on the extracted features; identifying a representative audio segment in each cluster; and selecting a representative audio segment as an audio summary of the audio piece.
 35. The method of claim 34, wherein each audio segment has a substantially equal rendering time.
 36. The method of claim 34, further comprising computing a feature vector centroid for each cluster, wherein each representative audio segment is closer to the feature vector centroid computed for the corresponding cluster than all other audio segments in the corresponding cluster.
 37. The method of claim 34, further comprising ranking clusters based on respective numbers of audio segments in the clusters.
 38. The method of claim 37, wherein a representative audio segment of a highest ranked cluster is selected as the audio summary. 